ci: publish server.json to the MCP Registry on release (GitHub OIDC)#2
Open
AlexDuchDev wants to merge 1 commit into
Open
ci: publish server.json to the MCP Registry on release (GitHub OIDC)#2AlexDuchDev wants to merge 1 commit into
AlexDuchDev wants to merge 1 commit into
Conversation
Adds .github/workflows/publish-mcp.yml — on a v*.*.* tag it installs mcp-publisher, authenticates with GitHub OIDC (no secrets), syncs server.json version to the tag, and publishes to registry.modelcontextprotocol.io.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wires up automated publishing of the existing
server.jsonto registry.modelcontextprotocol.io.What it does — on a
v*.*.*tag (or manual dispatch): installsmcp-publisher, authenticates via GitHub OIDC (no secrets, no browser login), syncsserver.jsonversionto the tag, and runsmcp-publisher publish. The repo's org (Moai-Team-LLC) authorizes theio.github.*namespace.Why OIDC + remotes —
server.jsonuses theremotestransport (self-hosted{baseUrl}/mcp), so no published npm/Docker artifact is needed; OIDC avoids any interactive login.Heads-up (first run): if publish fails with a permission/namespace error, the fix is almost always to lowercase the namespace in
server.json→io.github.moai-team-llc/agenticmind(GitHub-OIDC derives the namespace from the org login, typically lowercased). The schema itself allows mixed case, so I left your value as-is.To publish: merge, then push a tag (e.g.
git tag v0.3.1 && git push origin v0.3.1).